<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Definition of Done</title>
<script type="text/javascript" language="javascript" src="func.js"></script>
</head>

<body><img title="definition of done" src="../drawable/definition_of_done.jpg" width="100%"/>
<p>When the Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means. Although this varies significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency. This is the "Definition of Done" for the Scrum Team and is used to assess when work is complete on the product Increment.</p>
<a id = "a" href="#" onClick = "show('002', 'block');">Readmore...</a>
<span id = "002" style="display:none">
<p>The same definition guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning Meeting. The purpose of each Sprint is to deliver Increments of potentially shippable functionality that adhere to the Scrum Team's current Definition of "Done".</p>
<p>Development Teams deliver an Increment of product functionality every Sprint. This Increment is useable, so a Product Owner may choose to immediately release it. Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.</p>
<p>As Scrum Teams mature, it is expected that their Definition of "Done" will expand to include more stringent criteria for higher quality.</p>
</body>
</html>